Content sharing and storage of a plurality of remotely connected computing devices in physical or virtualized space

ABSTRACT

An information handling system includes a processor that executes instructions for a content sharing system having mixed operating system capabilities. The processor detects prepaired wireless connectivity remotely connected computing devices, and auto-initiates navigation accessibility within authorized remotely connected computing devices via the content sharing system. The information handling system also includes a display for a content sharing system desktop that includes representation of file structures corresponding to a plurality of remotely connected computing devices.

This application is a continuation of prior application Ser. No.14/674,962, entitled “Content Sharing and Storage of a Plurality ofRemotely Connected Computing Devices in Physical or Virtualized Space,”filed on Mar. 31, 2015, which is assigned to the current assignee hereofand is incorporated herein by reference in its entirety.

FIELD OF THE DISCLOSURE

The present disclosure generally relates to information handlingsystems, and more particularly relates to a thin computing system havingmixed OS capabilities for execution of a content sharing system locallyor via partial remote virtual computing and memory resources.

BACKGROUND

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option is an information handling system. An information handlingsystem generally processes, compiles, stores, or communicatesinformation or data for business, personal, or other purposes.Technology and information handling needs and requirements can varybetween different applications. Thus information handling systems canalso vary regarding what information is handled, how the information ishandled, how much information is processed, stored, or communicated, andhow quickly and efficiently the information can be processed, stored, orcommunicated. The variations in information handling systems allowinformation handling systems to be general or configured for a specificuser or specific use such as financial transaction processing, airlinereservations, enterprise data storage, or global communications. Inaddition, information handling systems can include a variety of hardwareand software resources that can be configured to process, store, andcommunicate information and can include one or more computer systems,graphics interface systems, data storage systems, networking systems,and mobile communication systems. Information handling systems can alsoimplement various virtualized architectures. Data and voicecommunications among information handling systems may be via networksthat are wired, wireless, or some combination. In some instances, usersmay operate via multiple computing devices. In other instances, multipleusers on multiple computing devices may want to collaborate and sharedata. Coordination of a wide variety of content from a variety ofdevices that may have disparate hardware requirements, softwarearchitecture, or distinct operating systems (OS) may be challenging.

BRIEF DESCRIPTION OF THE DRAWINGS

It will be appreciated that for simplicity and clarity of illustration,elements illustrated in the figures are not necessarily drawn to scale.For example, the dimensions of some elements may be exaggerated relativeto other elements. Embodiments incorporating teachings of the presentdisclosure are shown and described with respect to the drawings herein,in which:

FIG. 1 is a block diagram illustrating an information handling systemaccording to an embodiment of the present disclosure;

FIG. 2 is a block diagram illustrating a networked information handlingsystem having some or all of a content sharing system, and a pluralityof remotely connected computing devices according to an embodiment ofthe present disclosure;

FIG. 3 is a block diagram illustrating a content sharing systemaccording to one or more embodiments of the present disclosure;

FIG. 4 is a display image diagram illustrating a graphic user interface(GUI) for content sharing system desktop according to an embodiment ofthe present disclosure;

FIG. 5 is a flow diagram illustrating a method of navigation via acontent sharing system according to an embodiment of the presentdisclosure;

FIG. 6 is a flow diagram illustrating a method of exchange of filecontent via a content sharing system according to an embodiment of thepresent disclosure; and

FIG. 7 is a flow diagram illustrating a method of aggregation andorganization of file content from a plurality of remotely connectedcomputing devices via a content sharing system according to anembodiment of the present disclosure.

The use of the same reference symbols in different drawings indicatessimilar or identical items.

DETAILED DESCRIPTION OF THE DRAWINGS

The following description in combination with the figures is provided toassist in understanding the teachings disclosed herein. The descriptionis focused on specific implementations and embodiments of the teachings,and is provided to assist in describing the teachings. This focus shouldnot be interpreted as a limitation on the scope or applicability of theteachings.

FIG. 1 illustrates a generalized embodiment of information handlingsystem 100 for use with the present disclosures in multiple capacities.For purposes of this disclosure information handling system 100 caninclude any instrumentality or aggregate of instrumentalities operableto compute, classify, process, transmit, receive, retrieve, originate,switch, store, display, manifest, detect, record, reproduce, handle, orutilize any form of information, intelligence, or data for business,scientific, control, entertainment, or other purposes. For example,information handling system 100 can be a personal computer, a laptopcomputer, a smart phone, a tablet device or other consumer electronicdevice, a network server, a network storage device, a switch router orother network communication device, or any other suitable device and mayvary in size, shape, performance, functionality, and price. Further,information handling system 100 can include processing resources forexecuting machine-executable code, such as a central processing unit(CPU), a programmable logic array (PLA), an embedded device such as aSystem-on-a-Chip (SoC), or other control logic hardware. Informationhandling system 100 can also include one or more computer-readablemedium for storing machine-executable code, such as software or data.Additional components of information handling system 100 can include oneor more storage devices that can store machine-executable code, one ormore communications ports for communicating with external devices, andvarious input and output (I/O) devices, such as a keyboard, a mouse, anda video display. Information handling system 100 can also include one ormore buses operable to transmit information between the various hardwarecomponents.

Information handling system 100 can include devices or modules thatembody one or more of the devices or modules described above, andoperates to perform one or more of the methods described above.Information handling system 100 includes a processor 110, a chipset 120,a memory 130, a graphics interface 140, a disk controller 160, a diskemulator 180, an input/output (I/O) interface 150, and a networkinterface 170. Processor 110 is connected to chipset 120 via a processorinterface. Processor 110 is connected to memory 130 via a memory bus.Memory 130 is also connected to chipset 120 via the same or anothermemory bus. Graphics interface 140 is connected to chipset 110 andprovides a video display output to a video display 142. Video display142 is also connected to touch controller 144 and may be connected tochipset 120 via touch controller interface. In a particular embodiment,information handling system 100 includes separate memories that arededicated to processor 110 via separate memory interfaces. An example ofmemory 130 includes random access memory (RAM) such as static RAM(SRAM), dynamic RAM (DRAM), non-volatile RAM (NV-RAM), or the like, readonly memory (ROM), another type of memory, or a combination thereof.Memory 130 can store, for example, at least one application 132 andoperating system 134. Operating system 134 includes operating systemcode operable to detect resources within information handling system100, to provide drivers for the resources, initialize the resources, toaccess the resources, and to support execution of the at least oneapplication 132. Operating system 134 has access to system elements viaan operating system interface 136. Operating system interface 136 isconnected to memory 130.

Additionally, information handling system 100 may execute instructionsfor operating system conversion protocols via a processor 110 or chipset120 to enable files from multiple remotely connected computing deviceshaving a disparity of hardware, software architecture, and operatingsystem types to be interpreted and successfully operated with byoperating system 134. For example, information handling system 100 mayrun Linux kernel drivers with modules for a variety of OS systems andrelated file systems such as MS Windows, Apple OS, Android and similaroperating systems for connectable computing devices including phones,tablet computers, laptops, gaming systems, fitness devices, smartwatches, wearable computing devices, home or office environmentalcomputing systems and the like as would be understood by those of skillin the art. These kernel drivers for the OS system of the host 134 forthe content sharing system of the present disclosures are available tocommunicate and interpret alternate OS systems and file structures inremotely connected computing devices to the content sharing system. Fora variety of OS systems, conversion of certain file types may also beneeded for aggregation or file transfer functions of the content sharingsystem of the present disclosures example embodiments. In otherembodiments, information handling system 100 may communicate, interpret,or execute content files from a variety of source computing devices viaconversion to a common file type as is understood by those of ordinaryskill in the art which may be utilized in functions of aggregation andfile transfer exchanges done via the content sharing system of severalembodiments in the present disclosure. In an example, a common file typemay be conversion to IP protocol such as FTP.

Graphics interface 140, disk controller 160, I/O interface 150, andtouch controller 144 are connected to chipset 120 via interfaces thatmay be implemented, for example, using a Peripheral ComponentInterconnect (PCI) interface, a PCI-Extended (PCI-X) interface, ahigh-speed PCI-Express (PCIe) interface, another industry standard orproprietary communication interface, or a combination thereof. Chipset120 can also include one or more other I/O interfaces, including anIndustry Standard Architecture (ISA) interface, a Small Computer SerialInterface (SCSI) interface, an Inter-Integrated Circuit (I²C) interface,a System Packet Interface (SPI), a Universal Serial Bus (USB), anotherinterface, or a combination thereof.

Disk controller 160 is connected to chipset 120. Disk controller 160includes a disk interface 162 that connects the disc controller to ahard disk drive (HDD) 164, to an optical disk drive (ODD) 166, and todisk emulator 180. An example of disk interface 162 includes anIntegrated Drive Electronics (IDE) interface, an Advanced TechnologyAttachment (ATA) such as a parallel ATA (PATA) interface or a serial ATA(SATA) interface, a SCSI interface, a USB interface, a proprietaryinterface, or a combination thereof. Disk emulator 180 permits asolid-state drive 184 to be connected to information handling system 100via an external interface 182. An example of external interface 182includes a USB interface, an IEEE 1194 (Firewire) interface, aproprietary interface, or a combination thereof. Alternatively,solid-state drive 184 can be disposed within information handling system100.

In yet other embodiments, disk emulator 180 may work in connection witha remote desktop protocol or similar memory virtualization protocol tooperate a remote virtual storage device as if it were a device internalto computing system 100. In such a case, an external interface may beconnected form disk emulator 180 via a portion of network interface 170.Connection may be to network connected storage via a wireless or wirednetwork connection, for example, a WPAN/WLAN or other networkconnection.

I/O interface 150 is connected to chipset 120. I/O interface 150includes a peripheral interface 152 that connects the I/O interface toan add-on resource 154, and to a security resource 158. Peripheralinterface 152 can be the same type of interface as connects graphicsinterface 140, disk controller 160, and I/O interface 150 to chipset120, or can be a different type of interface. As such, I/O interface 150extends the capacity of such an interface when peripheral interface 152and the I/O channel are of the same type, and the I/O interfacetranslates information from a format suitable to such an interface to aformat suitable to the peripheral channel 152 when they are of adifferent type. Add-on resource 154 can include a data storage system,an additional graphics interface, a network interface card (NIC), asound/video processing card, another add-on resource, or a combinationthereof. As an example, add-on resource 154 is connected to data storagesystem 190 via data storage system interface 192. Add-on resource 154can be on a main circuit board, on separate circuit board or add-in carddisposed within information handling system 100, a device that isexternal to the information handling system, or a combination thereof.

Network interface 170 represents a NIC disposed within informationhandling system 100, on a main circuit board of the information handlingsystem, integrated onto another component such as chipset 120, inanother suitable location, or a combination thereof. Network interface170 is connected to I/O interface 150. Network interface device 170includes network channel 172 that provides an interface to devices thatare external to information handling system 100. In a particularembodiment, one or more network channels 172 are of a different typethan peripheral channel 152 and network interface 170 translatesinformation from a format suitable to the peripheral channel to a formatsuitable to external devices. An example of network channels 172includes InfiniBand channels, Fibre Channel channels, Gigabit Ethernetchannels, proprietary channel architectures, or a combination thereofsuitable for establishing WPAN, WLAN, WAN or other network connections.Network interface 170 may be a wireless interface or a wired interfacein various embodiments. Network channels 172 can be connected toexternal network resources (not illustrated). The network resource caninclude another information handling system, a data storage system,another network, a grid management system, another suitable resource, ora combination thereof.

FIG. 2 illustrates a generalized network 200 that can include one ormore information handling systems. In a particular embodiment, network200 includes networked mobile information handling systems 220, 222, and224, wireless network access points, and multiple wireless connectionlink options. Systems 220, 222, and 224 represent a variety of computingresources of network 200 including client mobile information handlingsystems. Additional resources may be available within network 240including data processing servers, network storage devices, local andwide area networks, or other resources as needed or desired. Asspecifically depicted, systems 220, 222, and 224 may be a laptopcomputer, tablet computer, or smartphone device. These user mobileinformation handling systems 220, 222, and 224, may access network 240.The user mobile information handling systems 220, 222, and 224 may alsoaccess a wider network via a macro-cellular network 250. Furtherresources may be available including additional data processing serverssuch as information handling system 210, remote data centers 290,additional network storage devices, additional local and wide areanetworks, or other resources as needed or desired. For example, network240 may be a wireless local area network (WLAN), a wireless personalarea network (WPAN), or a wireless wide area network (WWAN). Since WPANor WiFi Direct Connection and WWAN networks can functionally operatesimilar to WPAN/WLANs, they may be considered as wireless local areanetworks (WPAN/WLANs) for purposes herein. Wireless communicationsacross wireless local area network 240 may be via standard protocolssuch as IEEE 802.15.1 Bluetooth SIG, IEEE 802.11 Wi-Fi, IEEE 802.11adWiGig, IEEE 802.15 WPAN or similar wireless network protocols.Alternatively, other available wireless links within network 200 mayinclude macro-cellular connections via one or more protocols including2G standards such as GSM, 2.5G standards such as GSM EDGE and GPRS, 3Gstandards such as W-CDMA/UMTS and CDMA 2000, or 4G standards such asWiMAX, LTE, and LTE Advanced. Mobile information handling systems 220,222, and 224 may connect to the external network via base stationlocations at service providers. Links to WPAN/WLAN 240 may be via thesemacro-cellular connections as well or via other connections as isunderstood.

In other aspects, components of a WPAN/WLAN 240 may be connected bywireline or Ethernet connections (not shown) to the wider externalnetwork 250 with access to additional resources as described aboveincluding additional information handling systems 210 for remoteprocessing or remote data centers 290. For example, wireless networkaccess points may be connected to a wireless network controller and anEthernet switch. Connection between the wireless network 240 and a widernetwork 250 including information handling system 210 and remote datacenter 290 may be via Ethernet or another similar connection to theworld-wide-web, a WAN, a LAN, another WPAN/WLAN, or other networkstructure. Additional resources such as information handling system 210and remote data center 290 may host some or all of a content sharingsystem such as described in the present disclosure. In other aspects, ahost information handling system 210 and/or remote data center 290 mayconnect to WPAN/WLAN 240 in other embodiments. Such a connection viaWPAN/WLAN access point/Ethernet switch or via macrocellular connectionsto the external network may be a backhaul connection. The access pointmay be connected to one or more wireless access points in the WPAN/WLANbefore connecting directly to a mobile information handling system ormay connect directly to one or more mobile information handling systems220, 222, and 224.

The voice and packet core network 250 may access externally accessiblecomputing resources such as information handling system 210 and connectto remote data centers 290 as described. The voice and packet corenetwork 250 may contain multiple intermediate web servers or otherlocations with accessible data (not shown). Remote data center 290 mayinclude web servers or resources within a cloud environment. Forexample, remote data centers can include additional information handlingsystems, data processing servers, network storage devices, local andwide area networks, or other resources as needed or desired. Having suchremote capabilities may permit fewer resources to be maintained at theclient mobile information handling systems 220, 222, and 224 allowingstreamlining and efficiency within those devices. Similarly, remote datacenter 290 permits fewer resources to be maintained in other parts ofnetwork 200 such as at networked information handling system 210.

In an example embodiment, the cloud or remote data center 290 may runhosted applications for systems 220, 222, and 224 or for other networkedsystems such as information handling system 210. This may occur byestablishing a virtual machine application executing software to manageapplications hosted at the remote data center 290. Mobile informationhandling systems 220, 222, and 224 or information handling system 210may be adapted to run one or more applications locally, and to havehosted applications run in association with the local applications atremote data center 290. The virtual machine application may serve one ormore applications to each of user mobile information handling systems220, 222, and 224 and information handling system 210. Thus, asillustrated, systems 210, 220, 222, and 224 may be running applicationslocally while requesting data objects related to those applications fromthe remote data center 290 via wireless network.

For example, a content sharing system application may run locally atsystem 210. The content sharing system application may be associatedwith a host application that represents a content sharing system server.In another example, a data storage client application such as MicrosoftSharepoint may run on system 210. It may be associated with a hostapplication running at remote data center 290 that represents aSharepoint data storage server. In a further example, a web browserapplication may be operating at system 210. The web browser applicationmay request web data from a host application that represents a hostedwebsite and associated applications running at remote data center 290.Similarly, local applications may be run on remotely connectedinformation handling systems 220, 222, and 224 and associated with ahost application on information handling system 210 or remote datacenter 290 or some combination.

To communicate within the network 200, the systems 220, 222, and 224each have a wireless interface module or wireless adapter, hereinafterreferred to as a wireless adapter. The wireless adapters are operable toeach provide a wireless radio frequency interface to transmit andreceive voice and data between the respective systems 220, 222, and 224and one or more external networks via wireless network 240, 250, or awireline connection.

The wireless adapters can represent add-in cards, wireless networkinterface modules that are integrated with a main board of respectivesystems 220, 222, and 224 or integrated with another wireless networkinterface capability, or any combination thereof. In an embodiment thewireless adapters may include one or more radio frequency subsystemsincluding transmitters and wireless controllers for connecting via amultitude of wireless links. In an example embodiment, a mobileinformation handling system may have a transmitter for WiFi or WiGigconnectivity and one or more transmitters for macro-cellularcommunication. The radio frequency subsystems include wirelesscontrollers to manage authentication, connectivity, communications,power levels for transmission, buffering, error correction, basebandprocessing, and other functions of the wireless adapters.

The wireless adapters may be capable of connecting via a WPAN/WLAN 240or a macro-cellular network (WWAN) via a variety of the wirelessstandards or via wireline as described above. Each of the wirelessadapters for client mobile information handling systems 220, 222, and224 are uniquely identified on network 200 via one or more uniqueidentifiers permitting authentication and access. For example, thewireless device can each be identified by one or more SubscriberIdentity Modules (SIM), one or more of a media access control (MAC)address, an Internet protocol (IP) address, a worldwide name (WWN),Bluetooth UUID, or another unique identifier as needed or desired.Additional examples may assign a user name and password as a uniqueidentifier in some example embodiments. Association of a user and awireless interface module of a user information handling system may bemade via communications across a networking control plane. For example,a user information handling system may be associated with a user viacommunication with a database such as Home Subscriber Server (HSS),Active Directory or similar database.

The wireless adapters may operate in accordance with any wireless datacommunication standards. To communicate with wireless local area network140, standards including Bluetooth SIG, IEEE 802.11 WLAN standards, IEEE802.15 WPAN standards, WWAN such as 3GPP or 3GPP2, or similar wirelessstandards may be used. The WPAN/WLAN network 240 may provideconnectivity via Bluetooth, WiFi, or WiGig for example. The wirelessnetwork 240 may have a wireless mesh architecture in accordance withmesh networks described by the above wireless data communicationsstandards or similar standards. Wireless links may also connect to theexternal network via a WPAN, WLAN, or similar wireless switched Ethernetconnection. The wireless data communication standards set forthprotocols for communications and routing via access point, as well asprotocols for a variety of other operations. Other operations mayinclude handoff of client devices moving between nodes, self-organizingof routing operations, or self-healing architectures in case ofinterruption.

An information handling system 210 networked with a plurality ofinformation handling systems 220, 222, and 224 as illustrated in network200 may operate a content sharing system 230 according to variousembodiments. The content sharing system 230 may be series of executablecode instructions operating on a processor in information handlingsystem 210. In other embodiments, content sharing system 230 may be codeexecutable via a processing system on one or more a mobile informationhandling systems such as 220, 222, and 224 or may be remotely operatedvia remote data center 290. Content sharing system 230 in otherembodiments may be all or partly hard coded into an application specificprocessing system or may be distributed among several differentinformation handling systems for processing and execution. Informationhandling system 210 and content sharing system 230 may be connected viamacrocellular network, a wireline connection, a wider voice and packetcore network 250 or may be directly connected to WPAN or WLAN network240 or any combination of the same. As described above, content sharingsystem 230 may have mixed operating system capabilities in that plug-insor other processor commands may run via an content sharing systemoperating system allowing interfacing by the content sharing system 230with remotely connected information handling systems 220, 222, and 224as discussed further below. Information handling system 230 may beconnected to display 242 for displaying a content sharing system desktopfor interfacing, communication and executing commands to remotelyconnected information handling systems such as 220, 222, and 224.

Content sharing system 230 permits normalization of communication,functions, and sharing of files and data among information handlingsystems 220, 222, and 224 via a central information handling system 230.Files on information handling systems 220, 222, and 224 may be accessed,navigated and aggregated at a remote data center 290 or in remotestorage by the content sharing system 230. Operating system conversionfor data types and for commands permits control and navigation ofremotely connected information handling systems 220, 222, and 224 fromthe content sharing system 230 despite differing hardware, systemarchitectures, disparate operating systems and the like. Each remotelyconnected information handling system such as example systems 220, 222,and 224 may be represented on display screen 242 in the content sharingsystem desktop with a device environment-representative window. Thedevice environment-representative window corresponding to each remotelyconnected information handling system such as 220, 222, and 224 may beused in embodiments to assist with communication with the remotelyconnected information handling system 220, 222, and 224. Additionally,device environment-representative windows may be used for navigation andcontrol of applications and files with each corresponding respectiveremotely connected information handling systems 220, 222, and 224. Byuse of such a content sharing system 230 for communication, control, andoperation of remotely connected information handling systems 220, 222,and 224, collaboration among the connected computing devices andaggregation of files dispersed among the computing devices may beachieved in a more seamless and efficient manner on one content sharingdesktop. Information handling system 210 may operate as a thin shell OSclient with addition computing and storage for conversion amongoperating systems and architectures managed remotely via a remote datacenter with a plurality of servers such as shown at 290.

In various embodiments discussed in additional detail below, computingdevice environment-representative windows may display application anddata file trees showing architecture of files and executable codelocated on remotely connected information handling systems 220, 222, and224. In yet other embodiments, images of local desktops including iconsand control soft keys and other features may be replicated in the deviceenvironment-representative windows of the content sharing system 230 forone or more information handling systems 220, 222, and 224 where such areplication is possible or applicable. In some instances, remotelyconnected information handling systems 220, 222, and 224 may not haveany substantial desktop or navigation system. For example, this may bethe case for wearable technology such as a fitness computers, homecontrol systems, or other information handling systems that may beremotely connected. In yet other circumstances, desktop images or iconsof remotely connected information handling systems 220, 222, and 224 maybe proprietary or unwieldy to replicate in computing deviceenvironment-representative windows and a file tree or other similarstructure may be used instead.

More seamless control amongst varying remotely connected informationhandling systems 220, 222, and 224 may happen in execution of commands,communications, or navigation of system applications and data in eachinformation handling systems 220, 222, and 224 via the content sharingsystem 230. For example, in some embodiments, files may be transferredamong remotely connected information handling systems 220, 222, and 224with simple drag-and-drop or shortcut key functionality by collection ofthe file or data from a transferor computing device to the contentsharing system 230 and stored locally in storage at information handlingsystem 210 or stored remotely at a remote data center 290. The contentsharing system 230 may convert the file or data to an architecture orformat useable by the content sharing system 230 or may convert the fileor data to a format for the transferee system as necessary. In certainembodiments, the content sharing system desktop will indicate by visualcues that a file transfer has taken place or is taking place. Change incolor or highlighting of a file may indicate the change in file statusfor example. Additional visual cues will indicate which environment isbeing used when interfacing with the content sharing system desktop viadisplay 242 or via a remotely connected information handling system 220,222, or 224 in some embodiments.

In other aspects, the content sharing system 230 may aggregate files anddata from a plurality of remotely connected information handling systems220, 222, and 224. Data and files aggregated from a plurality ofremotely connected information handling systems such 220, 222, and 224may come from a variety of system hardware types, system architectures,or disparate operating systems and file or data formats. The contentsharing system 230 may interface with the remotely connected informationhandling systems such as 220, 222, and 224. Upon obtaining access,navigation of some or all files on information handling systems 220,222, and 224 will allow aggregation of permitted files to one shareddrive associated with the content sharing system 230. This may be ashared local drive at information handling system 210, may be a sharedvirtual drive such as at remote data center 290, or may be anycombination. The content sharing system 230 may use systems to organizeaggregated data from the plurality of remotely connected informationhandling systems. In this way, navigation of a complete set of data orfiles from the plurality of remotely connected information handlingsystems such as 220, 222, and 224 is more seamless and efficient.

Additionally, the content sharing system 230 may organize aggregatedfiles from a plurality of remotely connected information handlingsystems such as 220, 222, and 224 in a variety of ways. For example,files and data may be organized by OS type from which the file or datawas retrieved, or by computing device from which the data or files wereretrieved. In other examples, geotags or other location metadata may beused to organize files and data aggregated from a plurality of remotelyconnected information handling systems such as 220, 222, and 224 bygeographic region or location. For example, image, video, or audio dataand files may be organized from the plurality of remotely connectedinformation handling systems such as 220, 222, and 224 by location wherethe files were recorded. Similarly, aggregated data may be organized bychronology in another example of this aspect of the content sharingsystem 230.

In yet other examples, data may be organized according to how files andcontent are related to categories selected by the user or created by theuser via the content sharing system 230. For example, categories thatare designated personal, work-related, kid-related, or related otheractivity related may be used to organize aggregated files in sharedstorage by the content sharing system 230. Categorization criteria maybe varied in embodiments of the content sharing system aggregationaspect as is understood by those of skill in the art. Categories by filerelatedness to usage categories may assess factors such as where data orfiles come from, the type of files, identifying metadata for times,locations and other aspects of a file, or identifying content of thefiles. For example, a work based remotely connected information handlingsystem may contain files that are mixed work, personal, kids, and otheractivities. The source being a work computing device may weigh heavilytowards a work categorization, however a geotag or time stamp mayindicate that a file was created at a place or time not typicallyassociated with work. A file type may also play a factor in determininga categorization. For example a spreadsheet, word processing document orother file type may be more typically associated with a user's work thana video or photographic image. This would depend on designations of theuser or a learned trend of factors when categorizing relatedness tousage of aggregated files. Accordingly, the content sharing system 230may be able to further access the content of the files or data fromremotely connected information handling systems such as 220, 222, and224 to determine additional context for file categorization. Forexample, image or face recognition may be used to identify individualsin files. Scans of documents may identify names of an employer, a familymember, an organization name, project names, descriptions, titles,keywords or other information for classification purposes. In a sharedmemory environment, aggregated data from a plurality of remotelyconnected information handling systems such as 220, 222, and 224 maythen be reviewed and managed according to relatedness categorization.Additionally, operations may be performed on the aggregated files fromthe content sharing system location via remote desktop protocol orsimilar virtualization techniques. In other embodiments, operations,navigation of files including aggregated files may also be managed by auser from one of the remotely connected information handling systemssuch as 220, 222, and 224. In other words, access to or control of thecontent sharing system 230 under certain embodiments may be granted toone or more remotely connected information handling systems such as 220,222, and 224 via a similar virtualization protocol.

In one aspect of the present disclosure, automatic access by the contentsharing system may be requested or granted upon detection of remoteconnection by a remotely connected information handling systems such as220, 222, and 224 connecting to a network 240 monitored by contentsharing system 230. For example, the content sharing system 230 may polla monitored network, such as a wireless network 240 to monitor thenetwork for remotely connected or connecting information handlingsystems 220, 222, and 224 available for pairing with the wirelessnetwork and for pairing with the content sharing system. In someembodiments, remotely connected information handling systems such as220, 222, and 224 may have been pre-arranged as targets for contentsharing by the content sharing system 230. The remotely connectedinformation handling systems such as 220, 222, and 224 may have codeembedded in other embodiments to allow content sharing system 230 toinitiate access automatically upon connection with network 240 monitoredby the content sharing system. Content sharing system 230 may be set tomonitor any size network including one or more WPANs, WLANs, or othernetworks discussed. Upon approvals being granted by the remotelyconnected information handling systems such as 220, 222, and 224 and bythe content sharing system 230, navigation and access to files andcontent may be permitted via a content sharing system desktop. Securityfor pre-approved content sharing may streamline the access andnavigation process for the content sharing system 230 in someembodiments. The content sharing system 230 may then provide deviceenvironment-representative windows on the content sharing desktop toassist in navigation of the plurality of remotely connected informationhandling systems such as 220, 222, and 224 despite varying OS,architecture, and hardware.

In another aspect of the present disclosure, the content sharing system230 may enable remotely connecting devices such as 220, 222, and 224 toauto-pair wirelessly to the host information handling system 210 orremote data center 290 operating the content sharing system in someembodiments. The auto-pairing, which includes pairing to a wirelessnetwork and auto-initiation of access to the content sharing system, maybe pre-approved and permit approved remotely connecting informationhandling systems to efficiently be integrated into the content sharingsystem 230. Pre-approval may occur via data or code provided to someremotely connecting information handling systems 220, 222, and 224 inadvance of connecting to a network 240 monitored or associated with thecontent sharing system. Auto-pairing may also provide efficient andpre-approved access to network 240 by providing passcodes or otherinformation needed to pair with the wireless network in otherembodiments. Similarly, connection requirements to pair a remotelyconnected information handling system such as 220, 222, and 224 with thecontent sharing system 230 may be provided to permit auto-initiation ofaccess between the content sharing system 230 and the connecting device.Auto-pairing and auto-initiation are discussed further herein.

In another aspect, automatic execution of an aggregation of files maytake place upon remote connection by a plurality of information handlingsystems such as 220, 222, and 224 to a content sharing system 230 forone or more file types to be aggregated to allow a user to compare andreview files. Review of categorized files, for example, may be desirableto determine the scope of data and files stored across the systems ordetermine differences between similar or parallel files stored among theremotely connected information handling systems such as 220, 222, and224. Other automatic execution of applications and data files are alsocontemplated upon remote connection and confirmed accessibility of thecontent sharing system 230 and remotely connected information handlingsystems such as 220, 222, and 224.

In other aspects of the present disclosure, upon determination that oneor more remotely connected information handling systems such as 220,222, and 224 are accessible via the content sharing system 230, thecontent sharing system 230 may auto-execute certain files and data viaapplications on one or more information handling systems connectedwithin the WPAN or WLAN network. For example, upon connecting to thecontent sharing system 230, commands may be established to automaticallyoperate an application and execute one or more files. For example, aspreferences are learned by the system, a media player may determinefavored music file lists from among the one or more remotely connectedinformation handling systems such as 220, 222, and 224 and to play musicfrom that computing device.

In yet other aspects of the present disclosure, remotely connectedinformation handling systems 220, 222, and 224 may be owned or operatedby a plurality of users or organizations. In some cases, content sharingsystem 230 may be used with remotely connected information handlingsystems 220, 222, and 224 under control of one user. In other instances,remotely connected information handling systems 220, 222, and 224 may befrom a variety of users. For example, a group of collaborative usersfrom an organization may use the content sharing system 230. Use of suchthe content sharing system 230 for communication, control, and operationof remotely connected information handling systems 220, 222, and 224 maypose problems with respect to security, privacy or other considerationswhen devices originate from multiple sources. As a result, the contentsharing system may be set to classify remotely connected informationhandling systems 220, 222, and 224 according to roles they play fortheir user or users. Based on the roles played by remotely connectedinformation handling systems 220, 222, and 224, the content sharingsystem 230 may implement role-based policies to limit functions of thecontent sharing system such as those functions described above. Settingrole-based policies may be according to specific file types, metadata,expected purpose of files, identified users, or purposes of remotelyconnected computing devices as well as other factors described furtherbelow. Role-based policy settings may come from a policy controlinterface or may be received from remotely connected informationhandling systems 220, 222, and 224 as set by IT administrators for thosedevices.

FIG. 3 is a block diagram showing a hosted content sharing system 300according to an embodiment of the present disclosure. The contentsharing system host has a processor or an application specific processor305 for executing instructions to operate the content sharing system 330on host 300. Processor 305 may be connected via one or more buses asdescribed above to components including a wireless or wired networkinterface device 315, a display driver 320, or a memory controller 325.

In an example embodiment, the processor 305 operates a host operatingsystem (OS) 310 that may include Linux or another available operatingsystem. In some embodiments, host operating system 310 may be a thin OSwith association with a host application at a remote data center.Content sharing system host 300 further includes an OS system conversionprotocol 312. The OS conversion protocol 312 may include executable codeinstructions to detect an operating system or system architecture ofremotely connected information handling systems or their files. The OSconversion protocol will enable the files to be accessible by thecontent sharing system 330, navigated and communicated with via anavigation/communication module 360 of the content sharing system 330,and for functions to be performed or commands executed on the files fromvarious remotely connected information handling systems. For example, afile aggregator 342 may collect and aggregate all or a subset ofavailable files from the various remotely connected information handlingsystems to a local or remote shared memory location. A categorizationengine 344 may compare files from the various remotely connectedinformation handling systems based on location, timestamps, sources ofdata, file types, cues from metadata and content and other factors tocategorize and arrange the aggregated files in a variety of ways asdescribed.

Modification engine 346 may allow the content sharing system 330 to makemodifications to the aggregated files in shared storage and reflectthose changes on the remotely connected information handling systemswhere permitted. For example, a file may be copied between twoenvironment-representative windows 350 of the information handlingsystem via a copy short cut command or a drag and drop in the contentsharing system desktop 340. This copying may be done via a sharedstorage system and with OS conversion protocol to transfer the file. Inother embodiments, a transfer or copy function may be executed directlybetween remotely connected computing devices.

Execution engine 348 allows the content sharing system 330 to executefiles or applications in shared storage or on remotely connectedinformation handling systems via commands from the content sharingsystems 330. In an embodiment, commands may come through the contentsharing system 330 from other remotely connected information handlingsystems where permitted. For example, an auto execution of certain filesmay be set to run upon detected connection of remotely connectedinformation handling systems with the content sharing system 330 orafter aggregation of files by the file aggregator 342. In an exampleembodiment, a play list of audio files may be aggregated from aplurality of remotely connected information handling systems and an autoplay feature may be initiated from the aggregated audio files. Play mayproceed by favorites or preferences set by a user. In another example,data may be collected from one or more wearable fitness devices andanalysis software may be auto executed upon detection of interfacingwith the content sharing system 330. Viewable fitness data, both new andhistoric, may be auto-executed for viewing with a fitness trackingapplication.

The OS conversion protocol 312 may include use of kernel drivers for theOS system of the host 300. Additionally, one or more media sharingprograms are available for use, all or in part, as an OS conversionprotocol to communicate and interpret alternate OS systems and filestructures for remotely connected information handling systems. For avariety of OS systems, conversion of certain file types may also beneeded for functions such as aggregation or file transfer which willalso be accomplished by an OS conversion protocol 312. In someembodiments, content sharing system 330 may communicate, interpret, orexecute content files from a variety of remotely connected sourcecomputing devices via conversion to one or more common file types. Thefunctions of aggregation and file transfer exchanges may then be donevia the content sharing system according to several embodiments in thepresent disclosure. For example, conversion to IP protocol such as FTPmay be appropriate for certain file types.

Display driver 320 will drive a display associated with the host 300 ormay drive a remote display. Content sharing system 330 may have a modulefor establishing a content sharing system desktop 340 that may bedisplayed in an attached display device or a remote display. In otherembodiments, the content sharing system desktop 340 generated by thecontent sharing system 330 may be displayed on a remotely connectedinformation handling system, for example, via a wireless or wirednetwork interface. An example embodiment of a content sharing systemdesktop 340 is discussed further below but will include a plurality ofcomputing device environment-representative windows 350 corresponding toremotely connected information handling systems accessed by the contentsharing system 330. Those device environment-representative windows 350may include a file tree for navigation of files available to the contentsharing system 330. Navigation/communication module 360 allows forinteraction with the device environment-representative windows 350 tonavigate with or communicate commands with the applications on remotelyconnected information handling systems. Additionally,navigation/communication module 360 facilitates interaction with thedevice environment-representative windows 350 to interface withaggregated files in shared storage via memory controller 325 or networkinterface 315. Navigation/communication module 360 may be instrumentalalong with host OS 310 and processor 305 in administering limitations onthe content sharing system based on role-based policies determined toprovide ways to wall of sets of files and content from content sharingfunctions or from specific role-classified remotely connected computingdevices.

In another embodiment, images of a desktop from one or more remotelyconnected information handling systems is partially or completelyreplicated in a corresponding device environment-representative window350 of the content sharing system desktop 340. In other embodiments,visual cues in the content sharing desktop and deviceenvironment-representative windows may be used to identify remotelyconnected computing device role classifications. In some embodiments,visual cues in the content sharing system desktop and deviceenvironment-representative windows may indicate application of contentsharing system limitations according to role-based policies.

Memory controller 325 may connect externally directly or via a networkinterface with a virtual remote memory as shown or may interface with alocal shared memory storage. The virtual remote memory or local memorymay serve as a shared memory for the content sharing system. Sharedmemory may be used for navigation of files from remotely connectedinformation handling systems by the content sharing system 330.Additionally, a shared memory, local or remote, may be used by a fileaggregator 342, categorization engine 344, modification engine 346, andexecution engine 348 during aggregation of files from a plurality ofremotely connected information handling systems. Modification engine 346and execution engine 348 may also directly communicate vianavigation/communication module 360 with applications or files onremotely connected information handling systems as well.

FIG. 4 is a system 410 depicting content sharing system desktop 440 on adisplay device 442 associated with a host system of a content sharingsystem as described in the present disclosure. Remotely connectedinformation handling system 420 is shown with a corresponding deviceenvironment-representative window 450. Remotely connected informationhandling system 422 is shown with a corresponding deviceenvironment-representative window 452. In the present embodiment, deviceenvironment-representative windows 450 and 452 are shown as having acomplete or partial replication of the desktop interface found on theremotely connected information handling systems 420 and 422. A screenscrape of the remotely connected information handling systems 420 and422 may be used to replicate the remotely connected computing deviceuser interfaces. The content sharing system navigation module may thenassist with navigation of the remotely connected information handlingsystems 420 and 422 via the device environment-representative windows450 and 452. Icons in the device environment-representative windows maybe operated and commands may be executed remotely via a RDP or othervirtualization protocol with an execution engine and modification offiles may be modified accordingly with the modification engine. In otherembodiments, a file tree structure may be used with respect to one ormore of the device environment-representative windows instead asdescribed herein.

A file tree structure is shown in 465, but represents navigation andcommunication with aggregated files received from a plurality ofremotely connected information handling systems such as 420 and 422. InFIG. 4, aggregated file tree structure 465 may be organized according toremotely connected information handling system source devices 420 and422. In another embodiment, aggregated files may be categorizedaccording to a category designation that may be assessed and learned bythe content sharing system. For example in an embodiment, categoriesinclude home file, a sub file relating to kids, a work file, and avolunteer activity file. Other categorizations are contemplated as isunderstood. A command bar 460 is also shown in content sharing systemdesktop 440 and may be supported by the host operating system of thecontent sharing system of the present disclosures. The command bar 460may include commands for copying, aggregating, sorting, execution offiles and applications of the host for the content sharing system or forremotely connected information handling systems such as 420 and 422.Additionally, command bar 460 may include ways to interface with contentsharing system settings, security, or navigation tools for files anddata to facilitate the more seamless communication and utilization offiles and applications from among the plurality of remotely connectedinformation handling systems. Settings may include preferences relatingto auto-initiation of content sharing including identification ofremotely connected information handling systems, preferences foraggregation of files, determination of features of the deviceenvironment-representative windows, aggregation parameters andcategorization selections and other settings. The content sharing systemdesktop 440 may also have icons (not shown) for initiating variousoperations of the content sharing system. For example, content sharingsystem desktop icons may link to external sites for uploading ordownloading data or files. In another example embodiment, contentsharing system desktop icons may to applications available on thecontent sharing system or to initiate specific content sharing systemfunctions.

FIG. 5 is a flow diagram showing a method of content sharing amongremotely connected information handling systems according to anembodiment of the present disclosure. Method 500 begins at block 505. Atblock 505, the content sharing system identifies remotely connectedinformation handling systems for pairing to the content sharing system.In an example embodiment, the remotely connected information handlingsystems may be connected wirelessly to the host system for the contentsharing system or via a wired connection. Connection may be via a WPANsuch as Bluetooth detection or via a WLAN connection or other wirelessconnections as described herein in certain embodiments. Detection maycome about via an identification of remotely connected informationhandling systems by unique identifiers cross referenced with an approvedlist of computing devices accessible by the content sharing system. Inanother example embodiment, application code on a remotely connectedinformation handling system may initiate identification of the connectedinformation handling system as accessible by the content sharing system.In other instances, a user may initiate content sharing at the remotelyconnecting information handling systems by requesting accessibility tothe content sharing system after remote connection to the WPAN or WLAN.

In one example embodiment, the detection and access routine may beauto-initiated upon an information handling system being connected toone or more WPANs or WLANs being monitored by the information handlingsystem. In another example embodiment, the access to a remotelyconnected computing device may be an auto-initiation upon connection toone or more WPANs or WLANs having a content sharing system. As part ofautomatic initiation of access to a remotely connected informationhandling system, an RDP for virtualization of the remotely connectedinformation handling system may be initiated. In other examples, acookie or other code may be enabled to communicate availability of theremotely connected information handling system to the content sharingsystem upon connection to a WPAN or WLAN monitored by the contentsharing system. In yet other embodiments, the content sharing system mayrequest access to newly connected information handling systems to amonitored WPAN/WLAN if access is not already approved.

Proceeding to block 510, the content sharing system may verify access orsecurity levels set by an administrator of the content sharing system.The access security levels may include security controlling access tothe content sharing system by a remotely connected information handlingsystem. Verifying access and security levels at 510 may also include adetermination of whether a remotely connecting computing device permitsaccess to its files, and if so, whether some files and applications arerestricted. In another embodiment, the content sharing system maydetermine security risks posed by one or more remotely connectingcomputing devices to the content sharing system. For example, thecontent sharing system may determine whether access by a remotelyconnected information handling systems not behind a firewall may accessapplications, files and data of another remotely connected computingdevice under firewall protection. The content sharing system mayidentify restrictions for cross access between the computing devices orby the content sharing system. It is understood that security and accessmeasures may be taken in accordance with measures understood in the art.

If security is determined acceptable by the content sharing systemsettings, and access is granted to the content sharing system, thenavigation module of the content sharing system may initiate access atblock 515 to permitted files and applications on one or more remotelyconnected information handling systems. Access at block 515 may be via aRDP or other virtualization protocol for example.

Proceeding to decision block 520, the content sharing system willdetermine whether the OS on the remotely connected information handlingsystem matches that of the content sharing system host. In otherembodiments, the content sharing system may determine if the OS of theremotely connected information handling system is compatible with the OSof the content sharing system host computing device. In eitherembodiment, if the OS is not the same or compatible, the flow proceedsto block 525. At block 525, the content sharing system will utilize itsOS conversion protocols to enable communication with or access toapplications and files on the remotely connected information handlingsystem. Several example OS conversion protocol embodiments are discussedabove. Those, and similarly understood OS conversion protocols, areavailable for use with the disclosure herein.

Upon implementation of the OS conversion protocol or a determinationthat the remotely connected information handling system uses a similaror compatible OS to that of the content sharing system host, the flowthen proceeds to block 530. At block 530, the content sharing systempulls a hierarchy of files and applications with permitted access fromthe remotely connected information handling system. The content sharingsystem navigation module uses this file hierarchy or menu to accessfiles and content on the remotely connected information handlingsystems.

Flow may proceed to block 535. For embodiments where a computing deviceenvironment-representative window replicates a remotely connectedinformation handling system desktop, the content sharing system may pullimages of the remotely connected desktop including icons, control bars,and other features at block 535.

The flow proceeds to 540 where this desktop image data may be used tocreate a content sharing system desktop and interface with thenavigation module to establish navigation and control over the remotelyconnected information handling system via the corresponding deviceenvironment-representative windows. As explained, some deviceenvironment-representative windows of the content sharing desktop maysimply display a file tree hierarchy. Other file and applicationnavigation theme may be used in other embodiments. In embodiments whereremotely connected information handling system desktop images areavailable, the device environment-representative window may replicateall or part of a corresponding remotely connected information handlingsystem desktop.

Proceeding to block 545, the content sharing system may display thedevice environment-representative windows in the content sharing desktopon a local or remote display associated with the content sharing system.

At block 550 the content sharing system may assign visual cues to thedevice environment-representative windows. Colors, shading or othervisual cues may be used to indicate which deviceenvironment-representative windows are active or which windows arecurrently being utilized via the content sharing system. Other visualcues within the device environment-representative windows may indicateongoing execution of commands on the remotely connected informationhandling system, to indicate limited access to files and applications onthe remotely connected information handling system, or even to indicateactivity of specific applications or files within the deviceenvironment-representative windows representing the remotely connectedinformation handling system.

At this point, flow proceeds to block 555 where the content sharingsystem communicates and prepares commands to the remotely connectedinformation handling systems via a navigation and communication module.Such commands may come via a user using a systems settings userinterface of the content sharing system desktop or may be set up as autoinitiated by a user or administrator should certain conditions be met.In an embodiment, the navigation module is linked with the deviceenvironment-representative windows to permit navigation andcommunication of commands with a plurality of remotely connectedinformation handling systems of the content sharing system.

Proceeding to block 560, the content sharing system desktop may also usea set of visual cues in the content sharing desktop to indicate when thecontent sharing system is executing commands on one or more remotelyconnected information handling systems or functions of the contentsharing system such as aggregation. In an example, a visual cue mayindicate that a file is or has been copied between two remotelyconnected information handling systems from one deviceenvironment-representative window to another deviceenvironment-representative window. In another example, an image, videoor audio file may actively be being used via the content sharing systemor an application on one remotely connected information handling systemmay be running and visual cues may indicate the same. In another exampleembodiment discuss in further detail herein, visual cues may indicate indevice environment-representative windows which files or content areaggregated by the content sharing system and how those files arecategorized. At this point the flow may end. It is understood that thesequence of steps for the method blocks depicted in FIG. 5 is notlimiting and may occur in any order or some blocks may not occur at allduring optional embodiments of the present disclosures.

FIG. 6 is a flow diagram showing a method for navigation and exchange ofshared content via a content sharing system according to an embodimentof the present disclosure. Method 600 begins at block 610 where acommand is received via the content sharing system to transfer or copyfiles and content between a plurality of deviceenvironment-representative windows. The content sharing system desktopmay facilitate a number of ways for a user to execute a copy or transfercommand. For example, a file may be selected in a deviceenvironment-representative window and dragged to a second deviceenvironment-representative window as in 612. In another exampleembodiment, a right click copy or transfer command may be received bythe content sharing system desktop as in block 614. A keyboard shortcutfor copy or transfer may be used in yet another embodiment such as block616. In yet another embodiment, as in block 618, a copy or transfercommand may be selected from a command bar or menu of the contentsharing system desktop. Other copy or transfer commands may be indicatedby a user through the content sharing system desktop.

Upon receiving a copy or transfer command, the flow proceeds to block620. At 620, the content sharing system determines the source remotelyconnected information handling system and the connection with thatremotely connected computing device and the content sharing system.Proceeding to block 625, the content sharing system similarly determinesthe target remotely connected information handling system as a recipientof the transferred or copied content and the connection with thatremotely connected system.

Proceeding to 630, the content sharing system determines the OS orsystem architecture of the source and target remotely connectedinformation handling systems. At decision block 635, the content sharingsystem determines if there is a match between the OS of the source andtarget remotely connected information handling systems. Similarly,detection of the system architecture match for the source and targetremotely connected information handling systems in another embodimentmay be detected to determine if a conversion needs to be made by the OSconversion protocol module of the content sharing system.

If no match of OS, the flow proceeds to 640 where a transferred file isselected from the source remotely connected information handling systemsvia the navigation module of the content sharing system. The transferredfile is stored in shared storage of the content sharing system which maybe local or remote storage associated with the hosted content sharingsystem. Proceeding to 645, the content sharing system utilizes a hostAPI including plug-ins or other available OS conversion protocolfeatures to convert the file format to conform to or work compatiblywith the target remotely connected information handling system. In someembodiments, the conversion may be to a standard file format utilized bythe host OS for storage as an intermediate step before conversion to anOS type for the target remotely connected information handling system.The flow then proceeds to 655 where the content sharing system executesa copy or file transfer from the content sharing system storage to thetarget remotely connected information handling system. If the OS matchesat decision block 635, the flow proceeds to 650 where the contentsharing system stores the transferred file in shared storage of thecontent sharing system. As before, the flow then proceeds to 655 wherethe content sharing system executes a copy or file transfer from thecontent sharing system storage to the target remotely connectedinformation handling system.

Upon execution of the copy or transfer of the transferred file to thetarget remotely connected information handling system, the targetremotely connected information handling system receives the transferredfile via an API in local OS format at 660. Proceeding to 665, thecontent sharing system then initiates a visual cue at the source and/ortarget device environment-representative windows in the content sharingsystem desktop to indicate the change in status of the file or executionof the transfer command. At this point the flow may end. It isunderstood that the sequence of steps for the method blocks depicted inFIG. 6 is not limiting and may occur in any order or some blocks may notoccur at all during optional embodiments of the present disclosures.

FIG. 7 is a flow diagram showing a method for navigation and aggregationof shared content via a content sharing system according to anembodiment of the present disclosure. Method 700 begins at block 710where the content sharing system gains access to content and files on aplurality of remotely connected information handling systems inaccordance with the above described disclosure. In an exampleembodiment, a navigation module of the content sharing system obtainssuccessful access to the remotely connected information handlingsystems. This enables navigation of available files on the remotelyconnected information handling systems via the content sharing system.In an embodiment, the access is auto-initiated as described above.

Proceeding to decision block 715, the content sharing system determineswhether the OS on the remotely connected information handling systemsyielding access to files and content are the same or compatible to theOS of the host of the content sharing system. If not, the flow proceedsto block 720, where one or more OS conversion protocols are implementedby the content sharing system to make access of the files and contentavailable to the navigation module. The flow proceeds to block 725 afterOS conversion. Alternatively, if an OS match or compatibility is foundin decision block 715 flow proceeds to block 725.

At block 725, the content sharing system pulls file hierarchies from aplurality of remotely connected information handling systems. This maybe used, as in other embodiments, to generate deviceenvironment-representative window in the content sharing system desktop.

Proceeding to block 730, the content sharing system may determine whichfiles and content are not restricted by security measures implemented bythe remotely connected information handling systems or instituted by thecontent sharing system to prevent cross accessibility between computingdevices. For example, the content sharing system may restrict accessbetween remotely connected information handling systems having differingsecurity levels such as firewall protections or the like by determiningthe security status of the plurality of remotely connected informationhandling systems.

The flow proceeds to 735 where the content sharing system utilizes afile aggregator to pull accessible files and content from a plurality ofremotely connected information handling systems. The files and contentcopied from the plurality of remotely connected information handlingsystems may be stored into a remote or local shared storage for thecontent sharing system.

Proceeding to block 740, a categorization engine of the content sharingsystem may be initiated. The content sharing system will begin a sharedstorage categorization protocol according to settings of a user oradministrator of the content sharing system. Several categorizationthemes are shown as example embodiments. At 741, the aggregated filesmay be categorized and sorted by type of remotely connected informationhandling system to source the files. At 742, the aggregated files may becategorized and sorted by OS-type of the originating remotely connectedinformation handling systems. At 743, the aggregated files may becategorized and sorted by relatedness of content. Example relatednesscategories may be files associated with work, home, kids, school,volunteer activities, hobbies, and so forth. Determination ofcategorizing these files may come from determination of a number offactors as described above including chronology, location, sourcecomputing devices, metadata clues, file types or application types usedto run those files, content clues such as names or other descriptiveterms to name a few example criterion for determining relatednesscategorizations. At 744, the aggregated files may be categorized andsorted by geographic location of where files were created. For example,geotag information may be used to categorize files. At 745, theaggregated files may be categorized and sorted by chronology based ontimestamps relating to file creation. This may be varied according toearliest creation time of files, latest versions, or other timestampfactors of any time in between. At 746, the aggregated files may becategorized and sorted by security setting levels whereby files may beranked by sensitivity of content. This may include determiningsensitivity levels for files based on protection behind one or morefirewalls, encryption, pass code protection, designation in the files,or other security factors. At 749, it is contemplated that theaggregated files may be categorized and sorted by any number of othercategorization approaches. This may include multiple combinations of therecited bases for categorization of aggregated files and additionalsorting and categorizations commonly used with varying file types likelyto be aggregated from the plurality of remotely connecting informationhandling systems.

The flow proceeds to block 750 where files are aggregated by a fileaggregator of the content sharing system by copying the accessible filesfrom a plurality of remotely connected information handling systems intoa shared memory of the content sharing system. The categorization engineapplies a categorization protocol as described above to sort theaggregated files from the plurality of remotely connected informationhandling systems into a navigable hierarchy of files and sub-filesarranged by the aggregation engine. The content sharing system makes theaggregated files navigable and accessible by users of the system. In anexample embodiment, navigation of the aggregated files may be via a filehierarchy on the content sharing system desktop. In other embodiments,which may depend on security settings amongst the plurality of remotelyconnected information handling systems, the aggregated files may benavigated from one or more remotely connected information handlingsystems via the content sharing system. In this way, organization andnavigation of files from a plurality of remotely connected informationhandling systems, some with varying OS and file architectures, may beaccessed more seamlessly via one location. In another exampleembodiment, the aggregation of permitted files from the remotelyconnected information handling systems may be auto-aggregated upondetection of the remotely connected information handling system via theWPAN, WLAN or other network connection by the content sharing system. Invarious embodiments, auto-aggregation may take place upon similarconnection identification techniques to those described elsewhere withrespect to initiation of a navigation module of the content sharingsystem. For example, auto-aggregation may occur by detection of aconnection and sending a request for access to a remotely connectinginformation handling system. In other examples, a list of systems withunique identifiers that may be remotely connected to the content sharingsystem may be stored by the content sharing system and auto-initiateaggregation should a unique identifier match. It is understood that eachremotely connected information handling system may have a plurality ofunique identifiers depending upon the network type through which it isconnected. For example, a WPAN identifier may be different from a WLANidentifier. In other instances they may be the same. In yet anotherembodiment, software code such as an application or cookie on a remotelyconnected information handling system may identify that the system isaccessible by the content sharing system upon connection.

The flow proceeds to decision block 755 where the content sharing systemdetermines whether auto-execution settings for applications and filesfrom one or more remotely connecting information handling systems havebeen triggered. If so, the flow proceeds to block 760 where the contentsharing system provides for execution of commands according to thesettings of a user or an administrator to run a program or application.The program or application may be run by a remote desktop protocol orsimilar system for virtual control over a remotely connected informationhandling system. In other instances, the program or application may berun directly from the host system for the content sharing system. Thefiles utilized by a program or application whether run through aremotely connected information handling system or on a host computingdevice of the content sharing system may be sourced from the aggregatedfiles of the shared memory for the content sharing system. In otherembodiments, the files on one or more remotely connected informationhandling systems may be used during auto-execution of programs orapplications.

After auto-execution of programs or applications occurs, or if noauto-execution is detected, the content sharing system may proceed to acondition where the session with the content sharing system ends. Thismay occur via user or administrator ending the content sharing system atthe host in an example embodiment. In other embodiments, the connectionby a remotely connected information handling system may be terminatedending that remotely connected information handling system interfacewith the content sharing system. In yet other embodiments, the contentsharing system may be ended automatically. For example, there may be alimitation on time periods for operation of a content sharing systemwith remotely connected information handling systems. In such aninstance upon expiration of time, the content sharing system session maybe ended automatically.

Proceeding to block 765 upon ending of a session with the contentsharing system, the content sharing system may purge the aggregatedfiles in shared storage copied from some or all remotely connectedinformation handling systems. In the example of one or more individualremotely connected information handling systems terminating interfacewith the content sharing system, files and content aggregated from thoseterminated remotely connected information handling systems may be purgedfrom the shared storage in an example embodiment. In other embodimentsof the present disclosure, it may be desirable to host the aggregatedfiles by the content sharing system even after one or more remotelyconnected information handling systems has terminated an interface. Theaggregated files and content may continue to be reviewed and utilized ina number of capacities by a user. In an example embodiment of such ascenario, retention of aggregated files and content may be limited tosituations where the remotely connected information handling systems areall owned or controlled by one user, household, business, or otherorganization where sharing content from multiple remotely connectedinformation handling systems is desired. Upon ending a session of thecontent sharing system by the host, all aggregated files and content maybe purged in certain embodiments. At this point the flow may end. It isunderstood that the sequence of steps for the method blocks depicted inFIG. 7 is not limiting and may occur in any order or some blocks may notoccur at all during optional embodiments of the present disclosures.

In accordance with at least one aspect, a user can coordinate a widevariety of content from a variety of devices that may have disparatehardware requirements, software architecture, or distinct operatingsystems (OS). For example, auto-initiation of access to remotelyconnected information handling systems to a content sharing system via aWPAN or WLAN enables immediate and more seamless navigation andoperation of content and files from the variety of devices via a singledesktop. On the content sharing system desktop, deviceenvironment-representative windows make available navigation ofpermitted content and files from the variety of corresponding devices inone location. In some embodiments, shared memory is available formanipulation, execution, or navigation of the files and content sharedvia the content sharing system described in the present disclosure.

In accordance with another aspect, a user can coordinate a wide varietyof content from a variety of devices that may have disparate hardwarerequirements, software architecture, or distinct operating systems (OS)via aggregation and categorization of files from the plurality ofremotely connected devices. For example, auto-initiation of aggregationof files and content from the remotely connected information handlingsystems to a content sharing system via a WPAN or WLAN enables immediateassessment of content and files from the variety of devices via a singledesktop according to desired categories. On the content sharing systemdesktop, device environment-representative windows make available accessand modification of permitted content and files from the variety ofcorresponding devices in one location and easy comparison of relatedcontent aggregated at the content sharing system. In some embodiments,shared memory is available for aggregation, manipulation, execution, ornavigation of the aggregated files and content shared via the contentsharing system described in the present disclosure.

In accordance with yet another aspect, the content sharing systemcommunicates via one user interface content sharing system desktop theshared content made accessible from a wide variety of content from avariety of devices that may have disparate hardware requirements,software architecture, or distinct operating systems (OS). Visual cuesfacilitate navigation, execution, manipulation, aggregation and otherfeatures made available in one location via the content sharing systemof the present disclosure. This visual cues may include colors,highlighting, icons, active icons, movement of features of the deviceenvironment-representative windows, file tree hierarchies, command bars,or icons available on the content sharing system desktop.

In the embodiments described herein, an information handling systemincludes any instrumentality or aggregate of instrumentalities operableto compute, classify, process, transmit, receive, retrieve, originate,switch, store, display, manifest, detect, record, reproduce, handle, oruse any form of information, intelligence, or data for business,scientific, control, entertainment, or other purposes. For example, aninformation handling system can be a personal computer, a consumerelectronic device, a network server or storage device, a switch router,wireless router, or other network communication device, a networkconnected device (cellular telephone, tablet device, etc.), or any othersuitable device, and can vary in size, shape, performance, price, andfunctionality.

The information handling system can include memory (volatile (e.g.random-access memory, etc.), nonvolatile (read-only memory, flash memoryetc.) or any combination thereof), one or more processing resources,such as a central processing unit (CPU), a graphics processing unit(GPU), hardware or software control logic, or any combination thereof.Additional components of the information handling system can include oneor more storage devices, one or more communications ports forcommunicating with external devices, as well as, various input andoutput (I/O) devices, such as a keyboard, a mouse, a video/graphicdisplay, or any combination thereof. The information handling system canalso include one or more buses operable to transmit communicationsbetween the various hardware components. Portions of an informationhandling system may themselves be considered information handlingsystems.

When referred to as a “device,” a “module,” or the like, the embodimentsdescribed herein can be configured as hardware. For example, a portionof an information handling system device may be hardware such as, forexample, an integrated circuit (such as an Application SpecificIntegrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), astructured ASIC, or a device embedded on a larger chip), a card (such asa Peripheral Component Interface (PCI) card, a PCI-express card, aPersonal Computer Memory Card International Association (PCMCIA) card,or other such expansion card), or a system (such as a motherboard, asystem-on-a-chip (SoC), or a stand-alone device).

The device or module can include software, including firmware embeddedat a device, such as a Pentium class or PowerPC™ brand processor, orother such device, or software capable of operating a relevantenvironment of the information handling system. The device or module canalso include a combination of the foregoing examples of hardware orsoftware. Note that an information handling system can include anintegrated circuit or a board-level product having portions thereof thatcan also be any combination of hardware and software.

Devices, modules, resources, or programs that are in communication withone another need not be in continuous communication with each other,unless expressly specified otherwise. In addition, devices, modules,resources, or programs that are in communication with one another cancommunicate directly or indirectly through one or more intermediaries.

Although only a few exemplary embodiments have been described in detailherein, those skilled in the art will readily appreciate that manymodifications are possible in the exemplary embodiments withoutmaterially departing from the novel teachings and advantages of theembodiments of the present disclosure. Accordingly, all suchmodifications are intended to be included within the scope of theembodiments of the present disclosure as defined in the followingclaims. In the claims, means-plus-function clauses are intended to coverthe structures described herein as performing the recited function andnot only structural equivalents, but also equivalent structures.

What is claimed is:
 1. A method comprising: executing instructions, viaa processor, for a content sharing system having mixed operating systemcapabilities; detecting pre-paired wireless connectivity and determiningremotely connected computing device authorization for access with thecontent sharing system; auto-initiating navigation accessibility withinauthorized remotely connected computing devices via the content sharingsystem; and aggregating data files from the authorized remotelyconnected computing devices and organizing the data files intocategories of work-related file designation and personal filedesignations based on source or content of the data files; anddisplaying, via a display device, a content sharing system desktopcomprising the data file categories representing file structurescorresponding to the authorized remotely connected computing devices;wherein at least two authorized remotely connected computing devicesfunction via different operating systems.
 2. The method of claim 1further comprising: detecting pre-paired wireless connectivity for asecond group of remotely connected computing devices for viewing filesvia the content sharing system without authorization for navigationaccess with the content sharing system.
 3. The method of claim 1 furthercomprising: displaying, via a display device, a content sharing systemdesktop comprising device environment-representative windows to providenavigation access to file structures of the plurality of remotelyauthorized connected computing devices via an operating systemconversion protocol.
 4. The method of claim 3 further comprising:initiating an exchange of file content between the plurality ofauthorized remotely connected computing devices via a drag-and-drop offiles between the device environment-representative windows in thecontent sharing system desktop.
 5. The method of claim 3 furthercomprising: retrieving screen desktop display data from authorizedremote computing devices for redisplay in deviceenvironment-representative windows of the content sharing systemdesktop, wherein the remote computing device desktops redisplayed areinteractive in the device environment-representative windows of thecontent sharing system desktop.
 6. The method of claim 1 furthercomprising: executing operations on files from a plurality of theauthorized remotely connected computing devices via the content sharingsystem desktop.
 7. The method of claim 1 further comprising: terminatingnavigation accessibility within authorized remotely connected computingdevices via the content sharing system upon expiration of a contentsharing session. retrieval of data files from the plurality of remotelyconnected computing devices for aggregation by the content sharingsystem; organizing aggregated data files into categories in the contentsharing system according to common characteristics of the aggregateddata files.
 8. An information handling system comprising: a processorexecuting instructions for a content sharing system having mixedoperating system capabilities; the processor detecting pre-pairedwireless connectivity and determining remotely connected computingdevice authorization for access with the content sharing system; theprocessor auto-initiating navigation accessibility within a plurality ofauthorized remotely connected computing devices via the content sharingsystem; and a display for displaying a content sharing system desktopcomprising the data file categories representing file structurescorresponding to the authorized remotely connected computing devices,wherein at least two of the plurality of authorized remotely connectedcomputing devices function via different operating systems.
 9. Theinformation handling system of claim 8 further comprising: the displaydevice displaying environment-representative windows in the contentsharing system desktop to provide navigation access to file structuresof the plurality of remotely authorized connected computing devices viaan operating system conversion protocol.
 10. The information handlingsystem of claim 8 wherein the navigation accessibility within theplurality of authorized remotely connected computing devices via thecontent sharing system is terminated upon termination of a contentsharing session.
 11. The information handling system of claim 8 whereinthe processor further executes instructions to exchange file contentbetween at least two of the plurality of authorized remotely connectedcomputing devices via the content sharing system desktop.
 12. Theinformation handling system of claim 8 further comprising: the processorexecuting operations on a file from one of the plurality of theauthorized remotely connected computing devices via the content sharingsystem desktop; and the display displaying a visual indicator that theoperation has been conducted on the content sharing system desktop. 13.The information handling system of claim 12 wherein the visual indicatoris a color change to a representation of the file in the content sharingsystem desktop on which the operations are being executed.
 14. Theinformation handling system of claim 8 further comprising: the processorreceiving a command from a first authorized remotely connected computingdevice to perform an operation on a file from a second authorizedremotely connected computing device; the processor executing theoperations on the file from the second authorized remotely connectedcomputing device via the content sharing system; and the content sharingsystem accessing a virtual memory to facilitate the operation on filecontent between the plurality of remotely connected computing devices.15. An information handling system comprising: a processor executinginstructions for a content sharing system having mixed operating systemcapabilities; the processor detecting pre-paired wireless connectivityand determining remotely connected computing device authorization foraccess with the content sharing system; the processor auto-initiatingnavigation accessibility within a plurality of authorized remotelyconnected computing devices via the content sharing system; a displayfor displaying a content sharing system desktop comprising data filecategories representing file structures corresponding to the authorizedremotely connected computing devices; the processor performing anoperation on a file from one of the authorized remotely connectedcomputing devices via the content sharing system, wherein at least twoof the plurality of authorized remotely connected computing devicesfunction via different operating systems.
 16. The information handlingsystem of claim 15 wherein the content sharing system providesnavigation access to the file structures of the plurality of authorizedremotely connected computing devices via an operating system conversionprotocol.
 17. The information handling system of claim 15 furthercomprising: the display for displaying a content sharing system desktopcomprising a representation of files available to be navigated withinthe plurality of authorized remotely connected computing devices. 18.The information handling system of claim 15 wherein the content sharingsystem further organizes files from the plurality of authorized remotelyconnected computing devices into navigable file structures according tocommon characteristics of the files from the plurality of authorizedremotely connected computing devices.
 19. The information handlingsystem of claim 15 wherein the content sharing system is declinednavigation access to high security files designated in at least one ofthe plurality of authorized remotely connected computing devices. 20.The information handling system of claim 15 wherein the content sharingsystem provides navigation access via a content sharing system desktoponly to files with usage relatedness designated as work related filesfrom the plurality of authorized remotely connected computing devices.